Methods and apparatuses for requesting/providing code phase related information associated with various satellite positioning systems in wireless communication networks

ABSTRACT

Methods and apparatuses are provided that may be used by one or more devices within in wireless communication network to request and/or provide code phase related information signals associated with various Satellite Positioning Systems (SPSs).

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of co-pending U.S. patent applicationSer. No. 12/480,499, entitled “Methods and Apparatuses ForRequesting/Providing Code Phase Related Information Associated withVarious Satellite Positioning Systems in Wireless CommunicationNetworks,” filed Jun. 8, 2009, which claims priority to ProvisionalPatent Application No. 61/061,229, entitled “Generic Code Phase Encodingfor GNSS System,” filed Jun. 13, 2008, the complete disclosures of bothof which are expressly incorporated in their entirety by referenceherein.

BACKGROUND

1. Field

The subject matter disclosed herein relates to wireless communicationnetworks and devices and more particularly to methods and apparatusesfor use by devices within a wireless communication network to requestand/or provide code phase related information associated with variousSatellite Positioning Systems (SPSs).

2. Information

Position determination processes may be used to estimate or otherwisedetermine a location of a device associated with a wirelesscommunication network. In a particular example, a position determinationprocess may be implemented to estimate location coordinates for a mobiledevice such as a cellular telephone or other like mobile station. Thereare a variety of techniques available to support position determinationprocesses. For example, a Satellite Positioning System (SPS) such as theGlobal Positioning System (GPS) and/or other like systems may be used toestimate the location of a mobile station. In the context of a wirelesscommunication network, certain position determination processes mayrequire that information and/or processing tasks be shared and/ordistributed between and/or among multiple devices. For example, incertain instances a mobile station may be assisted in some manner by oneor more other devices as part of a position determination process. As aresult, there is often a need for such devices to communicate in somemanner, for example, via one or more position determinationcommunication sessions over a wireless link. Thus, one or morepositioning protocols may be developed to enable such positiondetermination communication sessions and as such support positiondetermination processes.

SUMMARY

In accordance with certain aspects, certain example methods andapparatuses are provided for use in one or more devices within awireless communication network to request and/or provide code phaserelated information associated with various Satellite PositioningSystems (SPSs).

By way of example, a method may be implemented which includesestablishing a code phase origin reference value this may be based, atleast in part, on one or more position determination information signalsrepresenting a plurality of code phase values associated with at leastone SPS. The method may further include establishing a plurality ofencoded code phase values that correspond to the plurality of code phasevalues, wherein each of the plurality of encoded code phase values isassociated with the code phase origin reference value. The method mayalso include transmitting at least one message that includes signalsrepresenting the plurality of encoded code phase values and identifyingthe code phase origin reference value.

In certain example implementations, at least a portion of the pluralityof code phase values may be associated with different reference timevalues. In certain example implementations, the code phase originreference value may be independent of the different reference timevalues. In certain example implementations, the code phase originreference value may include an average of the plurality of code phasevalues.

In certain example implementations, the encoded code phase values mayinclude acquisition assistance information and the transmitted messagemay be sent by a location server to a mobile station. In certain otherexample implementations, the encoded code phase values may includepseudorange measurement information and the transmitted message may besent by a mobile station to a location server.

In certain example implementations, the SPS may include one or moreGlobal Navigation Satellite Systems (GNSSs) and the transmitted messagemay identify the GNSS and at least one GNSS resource associated with atleast one of the encoded code phase values. For example, in certainimplementations, a GNSS resource may include a GPS resource, an SBASresource, a QZSS resource, a GLONASS resource, a Galileo resource, aCompass/BeiDou resource, and/or the like. The GNSS resource may beassociated with at least one of a GNSS signal, a GNSS signal band, aspace vehicle (SV), and/or the like, for example.

In accordance with yet another aspect, a method may be provided whichincludes receiving at least one message having signals representing aplurality of encoded code phase values associated with one or more SPSand identifying a code phase origin reference value. The method may alsoinclude establishing a plurality of code phase values that correspond tothe plurality of encoded code phase values based, at least in part, onthe plurality of encoded code phase values and the code phase originreference value.

In certain example implementations, the received message may identify areference time value with which the plurality of code phase values maybe based, at least in part, along with the encoded code phase values andthe code phase origin reference value.

In certain example implementations, each of the code phase values may beestablished by subtracting the code phase origin reference value and acorresponding encoded code phase value from a reference time value. Insome example implementations, the reference time value may be associatedwith a local time value.

In certain example implementations, the message may be received by amobile station from a location server and include acquisition assistanceinformation signals. In certain other implementations, the message maybe received by a location server from a mobile station and includepseudorange measurement information signals.

In accordance with certain other aspects, a specific apparatus may beprovided for use in a wireless communication network. The specificapparatus may include, for example, at least a signal processor and atransmitter. The signal processor may be operatively enabled to accessposition determination information signals representing a plurality ofcode phase values associated with at least one SPS, establish a codephase origin reference value based, at least in part, on the positiondetermination information signals, and establish a plurality of encodedcode phase values corresponding to the plurality of code phase values.Here, for example, each of the encoded code phase values may beassociated with the code phase origin reference value. The transmittermay be operatively enabled to transmit at least one message thatincludes one or more signals representing the encoded code phase valuesand the code phase origin reference value.

In certain example implementations, the specific apparatus may include alocation server and the encoded code phase values may includeacquisition assistance information for use by a mobile station. Incertain other example implementations, the specific apparatus mayinclude a mobile station and the encoded code phase values may includepseudorange measurement information for use by a location server.

In accordance with yet another aspect, a specific apparatus may beprovided for use in a wireless communication network. The specificapparatus may include, for example, at least, a receiver and a signalprocessor. The receiver may be operatively enabled to receive at leastone message having signals representing a plurality of encoded codephase values associated with one or more SPS and a code phase originreference value. The signal processor may be operatively enabled toestablish a plurality of code phase values that correspond to theencoded code phase values based, at least in part, on the encoded codephase values and the code phase origin reference value.

In certain example implementations, the specific apparatus may include amobile station and the received message may include acquisitionassistance information signals sent by a location server. In otherexample implementations, the specific apparatus may include a locationserver and the received message may include pseudorange measurementinformation signals sent by a mobile station.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic block diagram illustrating an example wirelesscommunication network environment within which at least two devices maycommunicate with one another and initiate and/or otherwise support aposition determination process, in accordance with an implementation.

FIG. 2 is a schematic block diagram illustrating certain examplefeatures of a device that may initiate and/or otherwise support aposition determination process, in accordance with an implementation.

FIG. 3 is a flow-diagram illustrating an exemplary method that may beimplemented in one or more devices to initiate and/or otherwise supporta position determination process, in accordance with an implementation.

FIG. 4 is an example timeline diagram illustrating encoding and decodingtechniques using a code phase origin reference value as may beimplemented to support the sharing of acquisition assistance informationas part of a position determination process, in accordance with animplementation.

FIG. 5 is an example timeline diagram illustrating encoding and decodingtechniques using a code phase origin reference value as may beimplemented to support the sharing of pseudorange measurementinformation as part of a position determination process, in accordancewith an implementation.

DETAILED DESCRIPTION

Non-limiting and non-exhaustive aspects are described with reference tothe following figures, wherein like reference numerals refer to likeparts throughout the various figures unless otherwise specified.

Position determination processes may be used to estimate or otherwisedetermine a location of a device and in particular examples the locationof a mobile device such as a mobile station. There are a variety oftechniques available to support position determination processes. In thecontext of a wireless communication network, certain positiondetermination processes may require that information and/or processingtasks be distributed between and/or among multiple devices. For example,in certain instances a mobile station may be assisted in some manner byone or more other devices as part of a position determination process.As a result, there may be a need for such devices to communicate in somemanner, for example, via one or more communication sessions, e.g.,“position determination communication sessions” over a wireless link.One or more positioning protocols may be developed to enable suchposition determination communication sessions for supporting variousposition determination processes. Such positioning protocols may providefor code phase related information associated with a SatellitePositioning Systems (SPS), to be shared between devices such as a mobilestation and a location server.

Thus, in accordance with certain exemplary aspects, methods andapparatuses may be implemented in a location server, a mobile station,and/or other like device(s) and/or specific apparatuses therein within awireless communication network to establish, share and/or utilize codephase related information associated with various Satellite PositioningSystem(s) (SPS(s)) for example, as part of a position determinationprocess.

For example, methods and apparatuses may be implanted in a sendingdevice such that code phase values associated with various differentSPS/GNSS resources, some or all of which may be related to differentreference time values, are instead associated with a “generic” codephase origin reference value that may be established by the sendingdevice. The resulting encoded code phase values and the code phaseorigin reference value may then be transmitted in one or more messagesto a receiving device along with additional position determinationinformation. A receiving device may then re-establish corresponding codephase values based, at least in part, on a reference time and thereceived “generic” code phase origin reference value and the encodedcode phase values.

By way of example, an exemplary method may be provided for use in awireless communication network. Such method may be implemented in alocation server and/or a mobile station, for example. Such method mayinclude establishing a “generic” code phase origin reference valuebased, at least in part, on position determination information signalsrepresenting a plurality of code phase values associated with at leastone SPS. Such a method may also include establishing a plurality ofencoded code phase values corresponding to the plurality of code phasevalues, wherein each of the plurality of encoded code phase values isassociated with the “generic” code phase origin reference value. Such amethod may also include transmitting at least one message comprisingsignals representing the plurality of encoded code phase values andidentifying the code phase origin reference value.

In certain example implementations, at least a portion of the pluralityof code phase values may be associated with one or more, possiblydifferent, reference time values, however the “generic” code phaseorigin reference value may be established to be independent of thesevarious reference time values. By way of example but not limitation, a“generic” code phase origin reference value may be established as anaverage and/or other like value as may be determined from the pluralityof code phase values.

In certain example implementations, the plurality of encoded code phasevalues may comprise acquisition assistance information sent by alocation server to a mobile station, e.g., within a wirelesscommunication network using at least one Position Determination DataMessage (PDDM). In other example implementations, the plurality ofencoded code phase values may comprise pseudorange measurementinformation that may be sent (e.g., in at least one PDDM, or the like)by a mobile station to a location server.

In certain example implementations, the SPS may include at least oneGlobal Navigation Satellite System (GNSS) and the message may identifythe GNSS and/or at least one GNSS resource associated with an encodedcode phase value. By way of example but not limitation, a GNSS resourcemay include a GPS resource, an SBAS resource, a QZSS resource, a GLONASSresource, a Galileo resource, a Compass/BeiDou resource, and/or otherlike resources. By way of example but not limitation, a GNSS resourcemay be identified as being associated with a particular GNSS signal, aparticular GNSS signal band, and/or a particular space vehicle (SV).

By way of further example, another exemplary method may be provided foruse in a receiving device within a wireless communication network. Thus,for example, such a method may be implemented in a location server thatis enabled to receive pseudorange measurement information signals sentby a mobile station, or in a mobile station that is enabled to receiveacquisition assistance information signals sent by a location server.With this in mind, a method may include receiving at least one messagecomprising signals representing a plurality of encoded code phase valuesassociated with one or more SPS and identifying a “generic” code phaseorigin reference value. The method may also include establishing (e.g.,re-establishing) a plurality of code phase values corresponding to theplurality of encoded code phase values based, at least in part, on theplurality of encoded code phase values and the “generic” code phaseorigin reference value.

In certain example implementations, such a method may includeestablishing each of the plurality of code phase values by subtractingthe “generic” code phase origin reference value and a corresponding oneof the plurality of encoded code phase values from a reference timevalue. In certain implementations, the reference time value may includea local time value, which may or may not be synchronized with a “system”time (e.g., GNSS, CDMA, or the like).

In certain example implementations, an element within a PDDM may includea request element and/or a provide element that is compliant and/orotherwise operative with Telecommunications Industry Association (TIA)“IS-801-B” positioning protocol standard and/or an associatedThird-Generation Partnership Project 2 (3GPP2) positioning protocolstandard.

Positioning protocols have been developed and standardized for use inCDMA2000 and High Rate Packet Data (HRPD) wireless communicationnetworks, for example. One example positioning protocol is oftenreferred to by its standardization identity as “IS-801” in the TIApublished standards (or “C.S0022” in 3GPP2 published standards).Currently, there are two versions of this example positioning protocol.The first version is the initial version IS-801 version 1 (or C.S0022-0version 3.0), which will simply be referred to herein as IS-801-1. Thesecond version is IS-801 version A (or C.S0022-A version 1.0), whichwill simply be referred to herein as IS-801-A. It is expected that someform of IS-801-B will soon be finalized and identified in some manner byTIA and/or 3GPP2 (e.g., perhaps as IS-801 version B (or C.S0022-Bversion 1.0), and/or other like identifiers).

In accordance with certain aspects of the present description, it isrecognized that it may be beneficial to develop more advanced/robustpositioning protocol versions, such as, IS-801-B and/or otherpositioning protocol versions which may support a plurality of differentGNSS and/or different types/formats of GNSS code phase relatedinformation. Moreover, it is also recognized that positioning protocolversion negotiation processes may be employed within wireless networks,as needed, to allow various enabled devices to initiate and establish aposition determination communication session over a communicationchannel/link and through which certain such potentially varying types ofcode phase related information may be requested and/or provided in anefficient manner.

By way of example but not limitation, certain methods and apparatusesprovided herein may use one or more PDDMs which may be provided in oneor more transport messages in a manner that not only supports IS-801-B,but also legacy and/or future versions. Further still, certain methodsand apparatuses may support position determination processes in avariety of wireless communication networks, such as, e.g., an UltraMobile Broadband (UMB) network, a High Rate Packet Data (HRPD) network,a CDMA2000 1X network, and/or the like.

In accordance with certain aspects of the present description, variousmethods and apparatuses are provided which may be implemented in one ormore devices that may support a position determination process. By wayof example but not limitation, a device may include a mobile station, ora specific apparatus, such as, a base station, a location server (e.g. aPosition Determination Entity (PDE), Serving Mobile Location Center(SMLC), Gateway Mobile Location Center (GMLC), Standalone AGPS SMLC(SAS), SUPL Location Platform (SLP), etc.), and/or the like. Forexample, in certain implementations a mobile station and base stationmay be operatively enabled to communicate within a CDMA wirelesscommunication network, and/or other applicable type of wirelesscommunication network.

Methods and apparatuses may be implemented in such devices to allow thedevices to utilize a position determination communication sessionassociated with a position determination process. The positiondetermination communication session may utilize a negotiated positioningprotocol version, depending on the capabilities of the devices involved.Thus, the methods and apparatuses may be implemented to allow fordifferent positioning protocol versions within a network. The methodsand apparatuses may, for example, be enabled to allow for or otherwisesupport backward and/or forward compatibility between variouspositioning protocol versions within a network.

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, methods and apparatuses that would be known by one ofordinary skill have not been described in detail so as not to obscureclaimed subject matter.

Some portions of the detailed description which follow are presented interms of algorithms or symbolic representations of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and generally, is considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals, information, or the like. It should be understood, however,that all of these or similar terms are to be associated with appropriatephysical quantities and are merely convenient labels. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout this specificationdiscussions utilizing terms such as “processing,” “computing,”“calculating,” “determining”, “establishing”, or the like refer toactions or processes of a specific apparatus, such as a special purposecomputer or a similar special purpose electronic computing device. Inthe context of this specification, therefore, a special purpose computeror a similar special purpose electronic computing device is capable ofmanipulating or transforming signals, typically represented as physicalelectronic or magnetic quantities within memories, registers, or otherinformation storage devices, transmission devices, or display devices ofthe special purpose computer or similar special purpose electroniccomputing device. In the context of this particular patent application,the term “specific apparatus” may include a general purpose computeronce it is programmed to perform particular functions pursuant toinstructions from program software.

Attention is now drawn to FIG. 1, which is a schematic block diagramillustrating an example wireless communication network environment 100within which devices may communicate with one another and initiateand/or otherwise support a position determination process.

In this particular example, wireless communication network environment100 includes representative devices such as a mobile station (MS) 102,one or more base station(s) (BS) 104, one or more Satellite PositioningSystem(s) (SPS) 106, a network 108, and a location server 110. MS 102may communicate with BS 104 over one or more wireless communicationlinks. One or more of MS 102, BS 104, or location server 110 may acquireSPS signals transmitted by various transmitting resources of SPS 106,and/or otherwise be enabled to support certain position determinationprocesses associated with information available via SPS 106.

Although the representative devices in FIG. 1 are illustrated as beingcoupled by either wireless communication links or wired communicationlinks, it should be understood that in certain example implementationsat least some of the devices may be coupled together via one or morewired, fiber, and/or wireless communication link(s).

Unless specifically stated otherwise, as used herein, the term “locationserver” is intended to represent one or more devices and/or one or morespecific apparatuses therein that is/are enabled to support, at least inpart, such position determination processes. Thus, while illustrated asa separate device in the example shown in FIG. 1 that may communicatevia network 108 and/or a BS 104 with MS 102, it should be understoodthat in other implementations a “location server” may communicatedirectly and/or indirectly with MS 102 using one or more wired and/orone or more wireless communication links. Hence, in certain exampleimplementations, a location server may take the form of and/or otherwiseoperatively comprise one or more wireless transmitters, receivers,transceivers, one or more base stations, various wired and/or wirelessnetwork resources, one or more computing devices enabled as specificapparatuses, and/or other like computing and/or communication devices.With this in mind, where example references are made to a base station(BS) or a BS 104, it should be understood that such BS and/or BS 104 maycomprise a “location server” as broadly defined herein. Accordingly, theterms base station (BS) and location server are used interchangeably.Further still, in messages requesting and/or providing BS capabilities,etc., it should be understood that such requested information and/orprovided information may be associated with location servercapabilities, etc. As illustrated in FIG. 1, MS 102 may share(send/receive) messages 112 (e.g., PDDMs) with (to/from) a locationserver.

MS 102 and/or BS 104 may provide functionality, for example, through theuse of various wireless communication networks such as a wireless widearea network (WWAN), a wireless local area network (WLAN), a wirelesspersonal area network (WPAN), and so on. The term “network” and “system”are often used interchangeably. A WWAN may be a Code Division MultipleAccess (CDMA) network, a Time Division Multiple Access (TDMA) network, aFrequency Division Multiple Access (FDMA) network, an OrthogonalFrequency Division Multiple Access (OFDMA) network, a Single-CarrierFrequency Division Multiple Access (SC-FDMA) network, and so on. A CDMAnetwork may implement one or more radio access technologies (RATs) suchas CDMA2000, Wideband-CDMA (W-CDMA), and so on. CDMA2000 includes IS-95,IS-2000, and IS-856 standards. A TDMA network may implement GlobalSystem for Communications (GSM), Digital Advanced Phone System (D-AMPS),or some other RAT. GSM and W-CDMA are described in documents from aconsortium named “3rd Generation Partnership Project” (3GPP). CDMA2000is described in documents from a consortium named “3rd GenerationPartnership Project 2” (3GPP2). 3GPP and 3GPP2 documents are publiclyavailable. A WLAN may be an IEEE 802.11x network, and a WPAN may be aBluetooth network, an IEEE 802.15x, or some other type of network. Thetechniques may also be used for any combination of WWAN, WLAN and/orWPAN. As mentioned earlier, the techniques may be implemented for usewith a UMB network, a HRPD network, a CDMA2000 1X network, GSM, LTE,and/or the like.

SPS 106 may, for example, include one or more of the Global PositioningSystem (GPS), a modernized GPS, Galileo, GLONASS, a Satellite BasedAugmentation System (SBAS), Quasi-Zenith Satellite System (QZSS),Compass/BeiDou, NAVSTAR, and/or other like GNSS, a system that usessatellites from a combination of these systems, or any SPS developed inthe future, each referred to generally herein as a “SatellitePositioning System” (SPS).

Furthermore, the methods and apparatuses described herein may be usedwith position determination processes that utilize pseudolites or acombination of satellites and pseudolites. Pseudolites may includeground-based transmitters that broadcast a PN code or other ranging code(e.g., similar to a GPS or CDMA cellular signal) modulated on an L-band(or other frequency) carrier signal, which may be synchronized with SPStime. Each such transmitter may be assigned a unique PN code so as topermit identification by a remote receiver. Pseudolites may be used toaugment a SPS, for example, in situations where some SPS signals fromorbiting satellites might be unavailable, such as in tunnels, mines,buildings, urban canyons or other enclosed areas. Another implementationof pseudolites is known as radio-beacons. The term “satellite”, as usedherein, is intended to include pseudolites, equivalents of pseudolites,and possibly others. The term “SPS signals”, as used herein, is intendedto include SPS-like signals from pseudolites or equivalents ofpseudolites.

MS 102, in certain example implementations, may include a device such asa cellular or other wireless communication device, personalcommunication system (PCS) device, personal navigation device, a vehiclemountable navigation device, a tracking device, Personal InformationManager (PIM), Personal Digital Assistant (PDA), laptop or othersuitable device which may be capable of receiving wirelesscommunications.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in various combinations of hardware, firmware, and/orsoftware. For a hardware implementation, one or more processing unitsmay be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, electronic devices, other electronicunits designed to perform the functions described herein, or acombination thereof.

For a firmware and/or hardware/software implementations, certainmethodologies may be implemented with modules (e.g., procedures,functions, and so on) that perform the functions described herein. Anymachine readable medium tangibly embodying instructions may be used inimplementing the methodologies described herein. For example, softwarecodes may be stored in a memory of MS 102 and/or BS 104 and executed bya processing unit of the device. Memory may be implemented within aprocessing unit and/or external to the processing unit. As used hereinthe term “memory” refers to any type of long term, short term, volatile,nonvolatile, or other memory and is not to be limited to any particulartype of memory or number of memories, or type of media upon which memoryis stored.

If implemented in hardware/software, functions that implementmethodologies or portions thereof may be stored on and/or transmittedover as one or more instructions or code on a computer-readable medium.A computer-readable medium may take the form of an article ofmanufacture. A computer-readable medium may include computer storagemedia and/or communication media including any medium that facilitatestransfer of a computer program from one place to another. A storagemedia may be any available media that may be accessed by a computer orlike device. By way of example but not limitation, a computer-readablemedium may comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that may be used to carry or store desired program code inthe form of instructions or data structures and that may be accessed bya computer.

“Instructions” as referred to herein relate to expressions whichrepresent one or more logical operations. For example, instructions maybe “machine-readable” by being interpretable by a machine for executingone or more operations on one or more data objects. However, this ismerely an example of instructions and claimed subject matter is notlimited in this respect. In another example, instructions as referred toherein may relate to encoded commands which are executable by aprocessing unit having a command set which includes the encodedcommands. Such an instruction may be encoded in the form of a machinelanguage understood by the processing unit. Again, these are merelyexamples of an instruction and claimed subject matter is not limited inthis respect.

Reference is now made to FIG. 2, which is a schematic block diagramillustrating certain example features of a specific apparatus 200enabled to initiate and/or otherwise support a position determinationprocess. Apparatus 200 may, for example, be implemented in some formwithin MS 102, BS 104, location server 110, and/or other like devices,as applicable, to perform or otherwise support at least a portion of theexample techniques described herein.

Apparatus 200 may, for example, include one or more processing units202, memory 204, a transceiver 210 (e.g., wireless network interface),and (as applicable) an SPS receiver 240, which may be operativelycoupled with one or more connections 206 (e.g., buses, lines, fibers,links, etc.). In certain example implementations, all or part ofapparatus 200 may take the form of a chipset, and/or the like.

Processing unit 202 may be implemented using a combination of hardwareand software. Thus, for example, processing unit 202 may represent oneor more circuits configurable to perform at least a portion of a datasignal computing procedure or process related to the operation of device200. By way of example but not limitation, processing unit 202 mayinclude one or more processors, controllers, microprocessors,microcontrollers, application specific integrated circuits, digitalsignal processors, programmable logic devices, field programmable gatearrays, and the like, or any combination thereof.

Memory 204 may represent any data storage mechanism. Memory 204 mayinclude, for example, a primary memory and/or a secondary memory.Primary memory may include, for example, a random access memory, readonly memory, etc. While illustrated in this example as being separatefrom processing unit 202, it should be understood that all or part of aprimary memory may be provided within or otherwise co-located/coupledwith processing unit 202. Secondary memory may include, for example, thesame or similar type of memory as primary memory and/or one or more datastorage devices or systems, such as, for example, a disk drive, anoptical disc drive, a tape drive, a solid state memory drive, etc.

In certain implementations, secondary memory may be operativelyreceptive of, or otherwise configurable to couple to, computer readablemedium 220. As such, in certain example implementations, the methodsand/or apparatuses presented herein may take the form in whole or partof a computer readable medium 220 that may include computerimplementable instructions 208 stored thereon, which if executed by atleast one processing unit 202 may be operatively enabled to perform allor portions of the example operations as described herein.

As illustrated in FIG. 2, memory 204 may also include instructionsand/or information in the form of data signals associated with, forexample, a code phase origin reference value 230, various positiondetermination information 232, one or more code phase values 234, one ormore encoded code phase values 236, one or more different reference timevalues 238, various acquisition assistance information 242, variouspseudorange measurement information signals 244, and/or other likeinformation.

Thus, for example, apparatus 200 may be implemented in location server110 (FIG. 1), which may provide acquisition assistance information to MS102. Here, for example, all or portions of acquisition assistanceinformation 242 may be requested by and/or otherwise provided to MS 102via one or more messages 112 (see FIG. 1). Acquisition assistanceinformation 242 may be associated with one or more SPS/GNSS resources.Acquisition assistance information 242 may include code phase values 234that may be associated (e.g., measured or otherwise related in somemanner) to one or more different reference time values 238. For example,acquisition assistance information 242 may include code phase valuesassociated with an SPS, GNSS, CDMA, and/or other like time reference. Asillustrated in FIGS. 3-5, and further described in greater detail below,apparatus 200 may also establish a “generic” code phase origin referencevalue 230 and based, at least in part thereon, further establish encodedcode phase values 236. For example, processing unit 202 may include asignal processing unit or the like that may access and process codephase values 234 to establish “generic” code phase origin referencevalue 230. Processing unit 202 may then establish encoded code phasevalues 236 corresponding to code phase values 234 based, at least inpart, on the “generic” code phase origin reference value 230. As usedherein, the term “generic” implies that the established code phaseorigin reference value 230 is used for all or at least a plurality ofencoded code phase values that may be included in the one or moremessages that are transmitted/received and may be based, at least inpart, on the corresponding code phase values.

An apparatus 200 may be implemented in mobile station 102 (FIG. 1),which may request/receive acquisition assistance information from alocation server. Here, for example, all or portions of acquisitionassistance information 242 may be received by MS 102 via one or moremessages 112 (see FIG. 1). For example, encoded code phase values 236and a “generic” code phase origin reference value 230 may be received.Processing unit 202 may “re-establish” code phase values 234corresponding to encoded code phase values 236 based, at least in part,on the “generic” code phase origin reference value 230.

If apparatus 200 is implemented in MS 102, for example, then SPSreceiver 240 may receive SPS signals associated with one or moreSPS/GNSS resources, and more particularly to attempt to receive andacquire certain GNSS signals based, at least in part, on acquisitionassistance information 242 as received from a location server.

In other examples, apparatus 200 may be implemented in mobile station102 (FIG. 1), which may provide pseudorange measurement information tolocation server 110. Here, for example, all or portions of pseudorangemeasurement information 244 may be requested by and/or otherwiseprovided to location server 110 via one or more messages 112 (see FIG.1). Pseudorange measurement information 244 may be associated with oneor more SPS/GNSS resources and established, for example, by SPS receiver240. Pseudorange measurement information 244 may include code phasevalues 234 that may be associated (e.g., measured or otherwise relatedin some manner) to one or more different reference time values 238. Forexample, pseudorange measurement information 244 may include code phasevalues associated with a time reference of an SPS, GNSS, CDMA, local MStime, and/or the like. As illustrated in FIGS. 3, 6 and 7, and furtherdescribed in greater detail below, apparatus 200 may also establish a“generic” code phase origin reference value 230 and based, at least inpart thereon, further establish encoded code phase values 236. Forexample, processing unit 202 may include a signal processing unit or thelike that may access and process code phase values 234 to establish“generic” code phase origin reference value 230. Processing unit 202 maythen establish encoded code phase values 236 corresponding to code phasevalues 234 based, at least in part, on the “generic” code phase originreference value 230.

An example apparatus 200 may be implemented in location server 110 (FIG.1), which may request/receive pseudorange measurement information from amobile station. Here, for example, all or portions of pseudorangemeasurement information 244 may be received by location server 110 viaone or more messages 112 (see FIG. 1). For example, encoded code phasevalues 236 and a “generic” code phase origin reference value 230 may bereceived. Processing unit 202 may “re-establish” code phase values 234corresponding to encoded code phase values 236 based, at least in part,on the “generic” code phase origin reference value 230. As is wellknown, pseudorange measurements from a mobile station may be used by alocation server to further assist in various position determinationprocesses.

Transceiver 210 may, for example, include a transmitter 212 enabled totransmit one or more electromagnetic signals over one or more wirelesscommunication links and a receiver 214 to receive one or more signalstransmitted over one or more wireless communication links. In certainimplementations, transceiver 210 may also support wired transmissionand/or reception, e.g., if implemented within BS 104, location server110, and/or other like devices.

Attention is drawn next to FIG. 3, which is a flow-diagram illustratingan exemplary method 300 that may be implemented in wirelesscommunication network environment 100 to support a positiondetermination process and more particularly, to support devices inrequesting and providing code phase related information signals.

At block 302, a “generic” code phase origin reference value may beestablished, for example, based on a plurality of code phase valuesassociated with one or more SPS/GNSS resource(s). At block 304, aplurality of encoded code phase values corresponding to the plurality ofcode phase values may be established, for example, using the “generic”code phase origin reference value.

At block 306, one or more messages with one or more encoded code phasevalue(s) and the code phase origin reference value may be sent through awireless communication network to a receiving device. Here, for example,a location server may send one or more PDDM(s) (e.g., a Provide GNSSAcquisition Assistance PDDM, or the like) to a mobile station. Here, forexample, a mobile station may send one or more PDDM(s) (e.g., a ProvideGNSS Pseudorange Measurement PDDM, or the like) to a location server.

At block 308, a receiving device may establish/re-establish one or morecode phase value(s) associated with the applicable SPS/GNSS resource(s)using the one or more received encoded code phase value(s) and “generic”code phase origin reference value. Thus, for example, a location servermay receive a Provide GNSS Pseudorange Measurement PDDM, or the like,that was sent from a mobile station. The location server may thenestablish each of the plurality of code phase values by subtracting the“generic” code phase origin reference value and a corresponding one ofthe plurality of encoded code phase values from a reference time value.In other examples, a mobile station may receive a Provide GNSSAcquisition Assistance PDDM, or the like, that was sent from a locationserver. The mobile station may then establish each of the plurality ofcode phase values by subtracting the “generic” code phase originreference value and a corresponding one of the plurality of encoded codephase values from a reference time value.

Attention is drawn next to Table 1 (below), which illustrates certaininformation that may be included in an example Provide GNSS AcquisitionAssistance PDDM.

TABLE 1 Information Element Name Type Multi Presence Part numberInteger(1..16) Total number of parts Integer(1..16) Global informationrecord Optional >Reference time Integer(0..604799999) >Time referencesource Integer(0..15) Optional >Reference time uncertaintyInteger(0..127) Optional >Clock information Optional >>Clock biasInteger(−31..480) >>Standard deviation of clock bias Bit String(5)error >>CHOICE Reference base station identifier >>>1x_HRPD >>>>Pilot PNsequence offset Integer(0..511) >>>UMB >>>>Pilot ID Bit String(16) >Codephase origin Integer(0..127) GNSS information record 1 to<maxNUM_GNSS> >GNSS identifier Integer(1..16) >GNSS signal record 1 to<maxNUM_SIG> >>GNSS signal identifier Integer (1..8)Optional >>Satellite information record 1 to <maxNUM_SAT> >>>GNSSsatellite ID number Integer(0..63) >>>Code phaseInteger(−65536..65535) >>>Code phase window Integer(0..31) >>>0^(th)order Doppler Integer(−2048..2047) >>>1^(st) order DopplerInteger(−1024..1023) Optional >>>Doppler search window Integer(0..4)Optional >>>AZ-El information Optional >>>>Azimuth of the satelliteInteger(0..511) >>>>Elevation angle of the satelliteInteger(0..127) >>>Satellite health indicator Bit String(8)Optional >>>GNSS signals available Bit String(8) Optional >>>Choice GNSSspecific fields Optional >>>>GNSS_identifier_1 >>>>>L2C mode BitString(2) Optional >>>>GNSS_identifier_4 >>>>>Channel numberInteger(−7..13) Optional

As illustrated in Table 1, in accordance with certain exampleimplementations, a part number may be included to specify the partnumber of the GNSS Acquisition Assistance data. Also, a total number ofparts may be included specifying the total number of parts that the GNSSAcquisition Assistance data is divided into. A global information recordmay be included (optional in this example). Here, for example, if thepart number is set to ‘1’ then a location server may include this field.Otherwise, if this field is absent, a mobile station may use the sameglobal information record as it used in processing a previous part ofthis response element. A reference time may be included (e.g., as aninteger (0 . . . 604799999) with a scale factor of 1 ms). Here, forexample, a location server may set this field to (t mod 604,800,000),where t is a reference time in units of 1 ms, valid for this part of theresponse element, based on a time reference specified by a ‘timereference source’.

A ‘time reference source’ may be included (optional in this example) toindicate the type of time reference for which the acquisition assistanceis valid in this part of the response element. By way of example, incertain implementations, a ‘0’ value may indicate a CDMA time reference,a ‘1’ value may indicate a GPS time reference, a ‘2’ value may indicatea QZSS time reference, a ‘3’ value may indicate a GLONASS timereference, a ‘4’ value may indicate a Galileo time reference, a ‘5’value may indicate a Compass/BeiDou time reference, etc. In certainimplementations, the time reference source value may be optional. Forexample, if absent then the “time reference source” may be considered tobe a CDMA time reference.

A reference time uncertainty may be included (optional in this example)to indicate a single-sided uncertainty of the reference time field.Here, for example, an uncertainty r in microseconds may be calculated asfollows: r=0.0022×(((1+0.18)K)−1), where K is the value given in thereference time uncertainty field in the range from 0 to 127. Thus, forexample, a value of K=127 means any value of r higher than 2.961seconds.

Clock information may be included (optional in this example) to specify,for example, a clock correction for GPS time. A clock bias may beincluded, for example, as an integer (−31 . . . 480) with a scale factorof 0.5 μs. Here, for example, a location server may set this field to anestimated mobile station clock bias in units of 0.5 μs, in the rangefrom −15.5 μs to +240 μs. The clock bias may, for example, be computedas true GPS time minus a mobile station time reference. It is notedhere, that as part of a GPS fix, a computation yields an estimate of thediscrepancy between the time specified by the local clock and true GPStime. Thus, this parameter may report such a discrepancy. One cause ofthis discrepancy may be the propagation delay from a transmitting basestation to the mobile station, which in this computation will bepositive. Accordingly, the range allowed for this parameter is notsymmetric. Further, it is noted that a ‘code phase window’ may beincluded as part of a satellite information record to account for anuncertainty in an estimated mobile station location. Thus, clockinformation may provide additional information about the uncertainty ofthe mobile station time reference. Standard deviation of clock biaserror information may also be included to identify an estimated standarddeviation of the clock bias error.

As shown in Table 1, a reference base station identifier may be includedfor use with CDMA200 1X, HRPD, UMB base stations. For example, for aCDMA 1X or HRPD base station, a pilot PN sequence offset may be includedand set to the PN sequence offset of a pilot of the base station forwhich the provided ‘Clock bias’ is valid, relative to the zero offsetpilot PN sequence, in units of 64 PN chips, in the range from 0 PN chipsto 32,704 PN chips. For example, for a UMB base station a pilot ID maybe included and set to the Pilot ID of the base station for which theprovided ‘Clock bias’ is valid.

As shown in Table 1, a (“generic”) code phase origin reference value maybe included, which in this example, may be specified as an integer(e.g., between 0 and 127). In this example, the code phase originreference value may have a scale factor (e.g., 1 ms). Thus, by way ofexample but not limitation, a location server in this example may setthis field to the origin of the code phase values included in the GNSSinformation record provided in this part of the response element in therange from 0 to 127 ms. Hence, in certain implementations, a receivingmobile station may establish a reference epoch in ms for the providedcode phase values by subtracting the value of the code phase origin inms from the provided reference time field in ms.

As shown in Table 1, GNSS information record may be included for 1 to amaximum number of GNSS (maxNUM_GNSS). In this example, this field mayidentify the GNSS for which acquisition assistance parameters areincluded in this response element. A mapping of some example GNSSidentifier values to SPS/GNSS resources is shown in Table 2 (below).

TABLE 2 GNSS signal identifier; integer value ‘1’ ‘2’ ‘3’ ‘4’ ‘5’ ‘6’‘7’ ‘8’ GNSS GNSS signal identifier; bit string value identifier Bit 1Bit 8 value GNSS (LSB) Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 (MSB) ‘1’ GPSL1 C/A L1C L2C L5 — — — — ‘2’ SBAS L1 C/A — — — — — — — ‘3’ QZSS L1 C/AL1C L2C L5 — — — — ‘4’ GLONASS G1 G2 G3 — — — — — ‘5’ Galileo E1 E5a E5bE5a + E5b E6 — — — ‘6’ Compass/ B1 B1-2 B2 B3 — — — — BeiDou ‘7’ to ‘16’Reserved for — — — — — — — — future GNSS

In certain implementations, a GNSS signal identifier element may beincluded and used to identify a GNSS signal for a GNSS as identified by“GNSS identifier” for which acquisition assistance information signalsare provided. An exemplary mapping of GNSS signal identifier to someexample GNSS signals is shown in Table 2. This element may be optionalin certain implementation; thus, e.g., if absent a location server orother like device may select a GNSS signal corresponding to the integervalue ‘1’, for example, in accordance with Table 2.

As shown in Table 1, a satellite information record may be included tospecify up to a maximum number (maxNUM_SAT) of satellites (e.g., SVs). AGNSS satellite ID number may be included and set to the value of thesatellite ID number of the GNSS identified by GNSS identifier for whichthe satellite information is valid, for example, as specified in Table 3(below).

TABLE 3 GNSS identifier GNSS satellite ID Interpretation of GNSS valueGNSS number value satellite ID number ‘1’ GPS  ‘0’-‘62’ Satellite PRNSignal No. 1 to 63. ‘63’ Reserved. ‘2’ SBAS  ‘0’-‘38’ Satellite PRNSignal No. 120 to 158. ‘39’-‘63’ Reserved. ‘3’ QZSS ‘0’-‘4’ SatellitePRN Signal No. 193-197.  ‘5’-‘63’ Reserved. ‘4’ GLONASS  ‘0’-‘23’ SlotNumber 1 to 24. ‘24’-‘63’ Reserved. ‘5’ Galileo Not Specified NotSpecified ‘6’ Compass/ Not Specified Not Specified BeiDou ‘7’ to ‘16’Reserved for — — future GNSS

As shown in Table 1, a (encoded) code phase value may be included. Byway of example but not limitation, an “encoded” code phase value may bespecified as an integer (e.g., between −65536 and 65535) with a scalefactor of: 2-10 ms. Here, for example, a location server may set thisfield to a predicted code phase observable relative to a time indicatedby Code phase origin in units of 2-10 ms, in the range from −64 to(64-2-10) ms scaled by a nominal chipping rate of the GNSS signal.Hence, for example, a receiving mobile station may then establish(re-establish) a corresponding (expected) code phase in chips asfollows: (‘Reference time’−‘Code phase origin’−‘Codephase’)×10−3×nominal chipping rate of the assisted signal.

A code phase window may also be included and set to represent a totalsize of a two-sided symmetric code phase search window, for example, asshown in Table 4 (below).

TABLE 4 Code Phase Code phase Search Window window Value [milli seconds] ‘0’ undefined  ‘1’ 0.001  ‘2’ 0.002  ‘3’ 0.003  ‘4’ 0.004  ‘5’ 0.005 ‘6’ 0.006  ‘7’ 0.008  ‘8’ 0.010  ‘9’ 0.012 ‘10’ 0.014 ‘11’ 0.018 ‘120.022 ‘13 0.026 ‘14 0.030 ‘15’ 0.038 ‘16’ 0.046 ‘17’ 0.054 ‘18’ 0.062‘19’ 0.078 ‘20’ 0.094 ‘21’ 0.110 ‘22’ 0.126 ‘23’ 0.158 ‘24’ 0.190 ‘25’0.222 ‘26’ 0.254 ‘27’ 0.318 ‘28’ 0.382 ‘29’ 0.446 ‘30’ 0.512 ‘31’ 0.640

A 0th order Doppler may also be included and set, for example, to avalue of the 0th order Doppler, in units of 0.5 m/s, in the range from−1024 m/s to +1023.5 m/s. Here, for example, conversion between m/s andHz may be made by using a nominal wavelength of the assisted signal.

A 1st order Doppler may also be included (optional in this example) andhave a scale factor of 0.0002 m/s2. Here, for example, a location servermay set this field to a value of the 1st order Doppler, in units of0.0002 m/s2, in a range from −0.2048 m/s2 to 0.2047 m/s2. Here too,conversion between m/s2 and Hz/s may be made by using a nominalwavelength of the assisted signal.

A Doppler search window may be included (optional in this example) andset to represent a total size of a two-sided symmetric Doppler searchwindow, for example, as shown in Table 5 (below).

TABLE 5 Doppler search Doppler Search window Value Window [m/s] ‘0’ 40‘1’ 20 ‘2’ 10 ‘3’ 5 ‘4’ 2.5

As shown in Table 1, Azimuth-Elevation (AZ-El) information may beincluded, for example, to identify an azimuth and elevation of asatellite (SV). Here, for example, a location server may identify anazimuth of a satellite, in units of 0.703125 degrees, in the range from0 to 359.296875 degrees, where 0 degrees is True North and the angleincreases toward the East. Here, for example, a location server mayidentify an elevation angle of a satellite, in units of 0.703125degrees, in the range from 0 to 89.296875 degrees.

A satellite health indicator may be included (optional in this example)to identify a GNSS signal for a GNSS as identified by ‘GNSS identifier’.This field may, for example, include 8 bits, each of the LSB'srepresenting one GNSS signal, e.g., as specified in exemplary Table 2.If a satellite signal corresponding to this ‘GNSS satellite ID number’may be useable for position computation, the location server may set thecorresponding bit to ‘1’, otherwise the corresponding bit may be set to‘0’. Bits for which no signal is defined in Table 2 may be set to ‘0’.

A GNSS signals available field may be included (optional in thisexample), which, for example may have 8 bits, with each of the LSBsrepresenting one signal for the GNSS identified by ‘GNSS identifier’, asspecified in Table 2. If a satellite transmits ranging signalsrepresented by a bit of this field, then the location server may setthat bit to ‘1’; otherwise, the bit may be set to ‘0’.

As shown in Table 1, various optional GNSS specific fields may beincluded. For example, a “GNSS_identifier_(—)1” may be included if the‘GNSS identifier’ field is set to ‘1’ (e.g., GPS). A L2C mode may beincluded to indicate a type of modulation used by a satellite on the GPSL2 frequency, for example, as shown in Table 6 (below).

TABLE 6 L2C_MODE Value (binary) L2C Modulation Format ‘00’ No datamodulation ‘01’ C/A navigation message bits ‘10’ CNAV navigation messagebits ‘11’ Reserved

A “GNSS_identifier_(—)4” may be included, for example, if the ‘GNSSidentifier’ field is set to ‘4’ (e.g., GLONASS). A channel number may beincluded to indicate a GLONASS carrier frequency number of a satelliteindicated by the ‘GNSS ID number’ field.

Attention is drawn next to Table 7 (below), which illustrates certaininformation that may be included in an example Provide GNSS PseudorangeMeasurement PDDM.

TABLE 7 Information Element Name Type Multi Presence Part numberInteger(1..16) Total number of parts Integer(1..16) Global informationrecord Optional >Reference time Integer(0..14399999) >Time referencesource Integer(0..15) >Reference time uncertainty Integer(0..127)Optional >Code phase origin Integer(0..127) Pseudorange information 1 to<maxNUM_GNSS> >GNSS identifier Integer(1..16) >Satellite measurementrecord 1 to <maxNUM_SIG> >>GNSS signal identifierInteger(1..8) >>Measurement parameters 1 to <maxNUM_SAT> >>>GNSSsatellite ID number Integer(0..63) >>>Channel number Integer(−7..13)Optional >>>Code phase Integer(−134217728..134217727) >>>Pseudorangemeasurement error Bit String(7) Optional indicator >>>Pseudorange RMSerror Bit String(6) >>>Satellite pseudodopplerInteger(−32768..32767) >>>Satellite pseudodoppler RMS Bit String(6)Optional error >>>Satellite C/N₀ Integer(0..63) >>>Estimated pseudorangefalse Integer(0..3) Optional alarm probability >>>Pseudorange falsealarm range Integer(0..3) Optional >>>Carrier phase measurement Optionalinformation >>>>Accumulated delta range Integer(0..33554431) >>>>Carrierphase quality indicator Bit String(2)

As illustrated in Table 7, in accordance with certain exampleimplementations, a part number may be included to specify the partnumber of the GNSS Pseudorange Measurement data. Also, a total number ofparts may be included specifying the total number of parts that the GNSSPseudorange Measurement data is divided into.

A global information record may be included. Here, for example, if thepart number is set to ‘1’ then a mobile station may include this field.Otherwise, if this field is absent, a location server may use the sameglobal information record as it used in processing a previous part ofthis response element. A reference time may be included (e.g., as aninteger (0 . . . 14399999) with a scale factor of 1 ms). Here, forexample, a mobile station may set this field to (t mod 14,400,000),where t is a reference time in units of 1 ms based on a time referencespecified by a ‘time reference source’.

A ‘time reference source’ may be included to indicate a type of timereference that was used in obtaining the measurements included in thisresponse element part. By way of example, in certain implementations, a‘0’ value may indicate a CDMA time reference, a ‘1’ value may indicate aGPS time reference, a ‘2’ value may indicate a QZSS time reference, a‘3’ value may indicate a GLONASS time reference, a ‘4’ value mayindicate a Galileo time reference, a ‘5’ value may indicate aCompass/BeiDou time reference, etc. In certain implementations, the timereference source value may be optional, for example, if absent then the“time reference source” may be considered to be a CDMA time reference.

A reference time uncertainty may be included (optional in this example)to indicate a single-sided uncertainty of the reference time field.Here, for example, an uncertainty r in microseconds may be calculated asfollows: r=0.0022×(((1+0.18)K)−1), where K is the value given in thereference time uncertainty field in the range from 0 to 127. Thus, forexample, a value of K=127 means any value of r higher than 2.961seconds.

As shown in Table 7, a (“generic”) code phase origin reference value maybe included, which in this example, may be specified as an integer(e.g., between 0 and 127). In this example, the code phase originreference value may have a scale factor of 1 ms. As such, in certainimplementations, a receiving location server may establish a referenceepoch in ms for the provided code phase measurements by subtracting thevalue of the code phase origin in ms from the provided reference timefield in ms.

As shown in Table 7, pseudorange information record may be included for1 to a maximum number of GNSS (maxNUM_GNSS). In this example, this fieldmay identify the GNSS for which pseudorange measurements are included inthis response element. A mapping of some example GNSS identifier valuesto SPS/GNSS resources is shown in Table 2.

A satellite measurement record may be included for 1 to a maximum numberof signals (maxNUM_SIG). A GNSS signal identifier may be included toidentify a GNSS signal for a GNSS as identified by ‘GNSS identifier’ forwhich pseudorange measurements are included in this response element. Anexample mapping of ‘GNSS signal identifier’ to a specific GNSS signalfor the GNSS identified by ‘GNSS identifier’ is shown in Table 2.

Measurement parameters may be included for 1 to a maximum number ofsatellites (SVs) (maxNUM_SAT). A GNSS satellite ID number may beincluded and set to the value of the satellite ID number of the GNSSidentified by ‘GNSS identifier’ for which the pseudorange measurement isvalid, for example, as shown in Table 3. A channel number may beincluded (optional in this example) and set to indicate a GLONASScarrier frequency number of the satellite indicated by “GNSS satelliteID number”. This field is optional and may be present if “GNSSidentifier” field is set to ‘4’ (GLONASS).

A (encoded) code phase value may be included, for example, representedby an integer (e.g., between −134217728 and 134217727) with a scalefactor of 2-21 ms. Here, for example, a mobile station may set thisfield to a measured code phase from the (“generic”) code phase origin ina range from −64 to (64-2-21) ms. A receiving location server may, forexample, establish (re-establish) a corresponding code phase value inchips as follows: (‘Reference time’−‘Code phase origin’−‘Codephase’)×10−3×nominal chipping rate of the measured signal.

As shown in Table 7, a pseudorange measurement error indicator may beincluded (optional in this example) and set to indicate the type oferrors that may have affected the code phase measurement parametersincluded in this ‘Pseudorange information’ record. Here, for example,this field may include 7 bits, with each of the LSB's represents oneerror type. An example mapping of such bits is shown in Table 8 (below).Here, for example, if an error type may have occurred then the mobilestation may set the corresponding bit to ‘1’; otherwise the mobilestation may set the corresponding bit to ‘0’.

TABLE 8 Pseudorange measurement error indicator Value PseudorangeMeasurement Error Type Bit 1 (LSB) Satellite cross-correlation Bit 2Short multipath (less than 1.5 μs delay difference between paths) Bit 3Long multipath (more than or equal to 1.5 μs delay difference betweenpaths) Bit 4 Non-GNSS interference Bits 5-7 Reserved

As shown in Table 7, a pseudorange RMS error may be included and set toan estimated pseudorange RMS error for an applicable satellite. Here,for example, a “floating-point” representation may be employed whereinthe four most significant bits constitute the exponent and the two leastsignificant bits constitute the mantissa, e.g., as illustrated in theexample shown in Table 9 (below).

TABLE 9 RMS Error in Expo- Man- Pseudorange nent, tissa, Index Value,Floating-Point Measurement Value, X Y i = Y + 4 × X Value, f_(i) σ[meters] ‘0000’ ‘00’  0 0.125 α < 0.125 ‘0000’ ‘01’  1 0.1563 0.125 ≦ α< 0.1563 X Y 2 ≦ i ≦ 61 (1 + Y/4) × 2^((X−3)) f_(i−1) ≦ α < f_(i) ‘1111’‘10’ 62 6144 5120 ≦ α < 6144 ‘1111’ ‘11’ 63 Not applicable 6144 ≦ α

As shown in Table 7, a satellite pseudodoppler integer may be includedand set to a value of a measured satellite pseudodoppler, for example,in units of 0.04 m/s, in the range from −1310.72 m/s to +1310.68 m/s.

A satellite pseudodoppler RMS error may be included (optional in thisexample) and set to an estimated pseudodoppler RMS error for theapplicable satellite. Here, for example, a “floating-point”representation may be employed, wherein the four most significant bitsconstitute the exponent and the two least significant bits constitutethe mantissa, e.g., as shown in Table 10 (below).

TABLE 10 RMS Error in Expo- Man- Pseudodoppler nent, tissa, Index Value,Floating-Point Measurement Value, X Y i = Y + 4 × X Value, f_(i) α [m/s]‘0000’ ‘00’  0 0.02 σ < 0.02 ‘0000’ ‘01’  1 0.025 0.02 ≦ σ < 0.025 X Y 2≦ i ≦ 61 0.02 × (1 + Y/ f_(i−1) ≦ σ < f_(i) 4) × 2^(X) ‘1111’ ‘10’ 62983.04 819.20 ≦ σ < 983.04 ‘1111’ ‘11’ 63 Not applicable 983.04 ≦ σ

As shown in Table 7, a satellite C/N0 may be included and set to a valueof a satellite C/N0, for example, in units of 1 dB-Hz, in the range from0 dB-Hz to 63 dB-Hz. Here, for example, the value of the satellite C/N0may be referenced to an antenna connector and/or the like within amobile station. If an active antenna is employed (e.g., one with abuilt-in amplifier, or filter, or both), then C/N0 may be referenced tothe antenna port prior to any amplifier or filter.

An estimated pseudorange false alarm probability may be included(optional in this example) and set to represent an estimated false alarmprobability, e.g., the probability that the parameters returned in thissatellite record resulted more from a measurement of noise then from ameasurement of a true SPS signal. Table 11 (below) shows an exampleimplementation for setting an estimated pseudorange false alarmprobability.

TABLE 11 PR_FALSE_ALARM_PROB Pseudorange False Value (Binary) AlarmProbability, p ‘00’ p < 0.005 ‘01’ 0.005 ≦ p < 0.05 ‘10’ 0.05 ≦ p ‘11’Not computable

As shown in Table 7, a pseudorange false alarm range may be included(optional in this example) and set, for example according to Table 12(below), to represent a size of a two-sided code phase search window,e.g., a range of satellite code phases, over which a false alarm mayhave occurred.

TABLE 12 Pseudorange False PR_FALSE_ALARM_RANGE Alarm Range, r Value(binary) (GPS C/A code chips) ‘00’ r < 32 ‘01’ 32 ≦ r < 256 ‘10’ 256 ≦ r‘11’ Not computable

As shown in Table 7, carrier phase measurement information may beincluded, which may include an accumulated delta range set to a measuredaccumulated delta range, e.g., in units of 2-10 meters and in a rangefrom 0 to (32,768−2-10) meters. A carrier phase quality indicator may beincluded and set to a quality of the carrier phase measurement. Here,for example, a LSB may indicate a data polarity. Thus, if the data froman applicable satellite is received inverted, the mobile station may setthe LSB of this bit field to ‘1’. Conversely, if the data is notinverted, the mobile station may set the LSB to ‘0’. The MSB mayindicate whether the accumulation of carrier phase has been continuous(e.g., without cycle slips) since a previous measurement report. If thecarrier phase accumulation has been continuous, the mobile station mayset the MSB to ‘1’, otherwise the mobile station may set the MSB to ‘0’.

Attention is drawn next to FIG. 4, which is an illustrative timelinediagram showing an example encoding of code phase information that maybe implemented to establish encoded code phase values in acquisitionassistance information signals. Here, for example, a timeline 400 isshown with a resolution 402 of 1 ms. More specifically, in this example,a reference time is 10,001 ms as measured in multiples of 1 ms. Periods9917 and 9939 are shown in expanded form to illustrate a relationshipbetween two of a plurality of code phase values and encoded code phasevalues based, at least in part, on a code phase origin reference value.

Here, for example, based at least in part on a plurality of code phasevalues in the acquisition assistance information to be provided to amobile station, a location server may establish a code phase originreference value 404. Here, code phase origin reference value 404 hasbeen set at 82 ms (e.g., 10,001−9919 ms as measured in multiples of 1ms). As illustrated at period 9917, a code phase value for SVi may berepresented by an encoded code phase value 406 of 1.65 ms (e.g., usingmultiples of 2-10 ms and rounding (1.65/2−10)=1690). As illustrated inperiod 9939, a code phase value for SVj may be represented by an encodedcode phase value 408 of −20.74 ms (e.g., using multiples of 2-10 ms androunding (−20.74 ms/2−10)=−21,238). Such encoded code phase values andcode phase origin reference value may then be transmitted to the mobilestation.

The mobile station may then establish (re-establish) the code phasevalues (e.g., calculate the expected SVi and SVj code phase values(ranges)) as follows and illustrated in FIG. 4. For SVi, an estimatedrange 412 may be established as “Reference time”−“Code phase originreference value”−“(encoded) Code phase value forSVi”×2−10=10,001−82−1690×2−10=9917.3496 ms. For SVj, an estimated range410 may be established as “Reference time”−“Code phase origin referencevalue”−“(encoded) Code phase value forSVj”×2−10=10,001−82−(−21238×2−10)=9939.7402 ms.

Reference is made next to FIG. 5, which is an illustrative timelinediagram showing an example encoding of code phase information that maybe implemented to establish encoded code phase values in pseudorangemeasurement information signals. Here, for example, a timeline 500 isshown with a resolution 502 of 1 ms. More specifically, in this example,for the mobile station a reference time 514 (e.g., MS measurement epoch)is 216 ms as measured in multiples of 1 ms. Periods 137 and 145 areshown in expanded form to illustrate a relationship between two of aplurality of code phase values and encoded code phase values based, atleast in part, on a code phase origin reference value.

Here, for example, based at least in part on a plurality of code phasevalues in the pseudorange measurement information to be provided to alocation server, the mobile station may establish a code phase originreference value 504. In the illustrated example code phase originreference value 504 has been set at 76 ms (e.g., 216−140 ms as measuredin multiples of 1 ms).

As illustrated at period 137, a code phase value for SVN may be based onan observed SVN time tsvN=137.803 ms and have a corresponding encodedcode phase value 506 of 2.197 ms or round{2.197/2−21}=4607443. Asillustrated at period 145, a code phase value for SV1 may be based on anobserved SV1 time tsv1=145.312 ms and a corresponding encoded code phasevalue 508 of −5.312 ms or round{−5.312/2−21}=−11140071. Such encodedcode phase values and code phase origin reference value may then betransmitted to the location server.

The location server may then establish (re-establish) the code phasevalues based at least on part on the encoded code phase values and codephase origin reference value. For example, observed tsv1 may be“re-established” as =“Reference Time”−“Code phase origin referencevalue”−“(encoded) Code phase value”=216−76−(−11140071×2−21)=145.31199ms. For example, observed tsvN may be “re-established” as =“ReferenceTime”−“Code phase origin reference value”−“(encoded) Code phasevalue”=216−76−(4607443×2−21)=137.80299 ms.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein.

Therefore, it may be intended that claimed subject matter not be limitedto the particular examples disclosed, but that such claimed subjectmatter may also include all aspects falling within the scope of appendedclaims, and equivalents thereof.

What is claimed is:
 1. A method for use in a wireless communicationnetwork, the method comprising: receiving at least one messagecomprising signals representing a plurality of encoded code phase valuesassociated with one or more satellite positioning system(s) (SPS(s)) andidentifying a code phase origin reference value; and establishing aplurality of code phase values corresponding to said plurality ofencoded code phase values based, at least in part, on said plurality ofencoded code phase values and said code phase origin reference value. 2.The method as recited in claim 1, wherein said at least one messagecomprises signals identifying a reference time value, and whereinestablishing said plurality of code phase values comprises establishingsaid plurality of code phase values based, at least in part, on saidplurality of encoded code phase values, said code phase origin referencevalue, and said reference time value.
 3. The method as recited in claim1, wherein each of said plurality of code phase values is established bysubtracting said code phase origin reference value and a correspondingone of said plurality of encoded code phase values from a reference timevalue.
 4. The method as recited in claim 3, wherein said reference timevalue comprises a local time value.
 5. The method as recited in claim 1,wherein said at least one message comprises acquisition assistanceinformation signals sent by a location server to a mobile station. 6.The method as recited in claim 1, wherein said at least one messagecomprises pseudorange measurement information signals sent by a mobilestation to a location server.
 7. The method as recited in claim 1,wherein said at least one message comprises at least one PositionDetermination Data Message (PDDM).
 8. The method as recited in claim 1,wherein said at least one SPS comprises at least one Global NavigationSatellite System (GNSS) and said at least one message comprises signalsidentifying said at least one GNSS and at least one GNSS resourceassociated with at least one of said plurality of encoded code phasevalues.
 9. The method as recited in claim 8, wherein said GNSS resourcecomprises at least one of a GPS resource, an SBAS resource, a QZSSresource, a GLONASS resource, a Galileo resource, and/or aCompass/BeiDou resource.
 10. The method as recited in claim 8, whereinsaid GNSS resource is associated with at least one of a GNSS signal, aGNSS signal band, and/or a space vehicle (SV).
 11. A specific apparatusfor use in a wireless communication network, the specific apparatuscomprising: means for receiving at least one message comprising signalsrepresenting a plurality of encoded code phase values associated withone or more satellite positioning system(s) (SPS(s)) and identifying acode phase origin reference value; and means for establishing aplurality of code phase values corresponding to said plurality ofencoded code phase values based, at least in part, on said plurality ofencoded code phase values and said code phase origin reference value.12. The specific apparatus as recited in claim 11, wherein said at leastone message comprises signals identifying a reference time value, andwherein said means for establishing said plurality of code phase valuescomprises means for establishing said plurality of code phase valuesbased, at least in part, on said plurality of encoded code phase values,said code phase origin reference value, and said reference time value.13. The specific apparatus as recited in claim 11, wherein each of saidplurality of code phase values is established by subtracting said codephase origin reference value and a corresponding one of said pluralityof encoded code phase values from a reference time value.
 14. Thespecific apparatus as recited in claim 13, wherein said reference timevalue comprises a local time value.
 15. The specific apparatus asrecited in claim 11, wherein said at least one message comprisesacquisition assistance information signals sent by a location server toa mobile station.
 16. The specific apparatus as recited in claim 11,wherein said at least one message comprises pseudorange measurementinformation signals sent by a mobile station to a location server. 17.The specific apparatus as recited in claim 11, wherein said at least onemessage comprises at least one Position Determination Data Message(PDDM).
 18. The specific apparatus as recited in claim 11, wherein saidat least one SPS comprises at least one Global Navigation SatelliteSystem (GNSS) and said at least one message comprises signalsidentifying said at least one GNSS and at least one GNSS resourceassociated with said at least one of said plurality of encoded codephase values.
 19. The specific apparatus as recited in claim 18, whereinsaid GNSS resource comprises at least one of a GPS resource, an SBASresource, a QZSS resource, a GLONASS resource, a Galileo resource,and/or a Compass/BeiDou resource.
 20. The specific apparatus as recitedin claim 18, wherein said GNSS resource is associated with at least oneof a GNSS signal, a GNSS signal band, and/or a space vehicle (SV).
 21. Aspecific apparatus for use in a wireless communication network, thespecific apparatus comprising: a receiver operatively enabled to receiveat least one message comprising signals representing a plurality ofencoded code phase values associated with one or more satellitepositioning system(s) (SPS(s)) and identifying a code phase originreference value; and a signal processor operatively enabled to establisha plurality of code phase values corresponding to said plurality ofencoded code phase values based, at least in part, on said plurality ofencoded code phase values and said code phase origin reference value.22. The specific apparatus as recited in claim 21, wherein said at leastone message comprises signals identifying a reference time value, andwherein said signal processor is operatively enabled to establish saidplurality of code phase values based, at least in part, on saidplurality of encoded code phase values, said code phase origin referencevalue, and said reference time value.
 23. The specific apparatus asrecited in claim 21, wherein each of said plurality of code phase valuesis established by subtracting said code phase origin reference value anda corresponding one of said plurality of encoded code phase values froma reference time value.
 24. The specific apparatus as recited in claim23, wherein said reference time value comprises a local time value. 25.The specific apparatus as recited in claim 21, wherein said specificapparatus comprises a mobile station and said at least one messagecomprises acquisition assistance information signals sent by a locationserver.
 26. The specific apparatus as recited in claim 21, wherein saidspecific apparatus comprises a location server and said at least onemessage comprises pseudorange measurement information signals sent by amobile station.
 27. The specific apparatus as recited in claim 21,wherein said at least one message comprises at least one PositionDetermination Data Message (PDDM).
 28. The specific apparatus as recitedin claim 21, wherein said at least one SPS comprises at least one GlobalNavigation Satellite System (GNSS) and said at least one messagecomprises signals identifying said at least one GNSS and at least oneGNSS resource associated with at least one of said plurality of encodedcode phase values.
 29. The specific apparatus as recited in claim 28,wherein said GNSS resource comprises at least one of a GPS resource, anSBAS resource, a QZSS resource, a GLONASS resource, a Galileo resource,and/or a Compass/BeiDou resource.
 30. The specific apparatus as recitedin claim 28, wherein said GNSS resource is associated with at least oneof a GNSS signal, a GNSS signal band, and/or a space vehicle (SV). 31.An article comprising: a non-transitory computer readable medium havingcomputer implementable instructions stored thereon which if implementedby one or more processing units in a specific apparatus operativelyenable the specific apparatus to: access at least one message comprisingsignals representing a plurality of encoded code phase values associatedwith one or more satellite positioning system(s) (SPS(s)) andidentifying a code phase origin reference value; and establish aplurality of code phase values corresponding to said plurality ofencoded code phase values based, at least in part, on said plurality ofencoded code phase values and said code phase origin reference value.32. The article as recited in claim 31, wherein said at least onemessage comprises signals identifying a reference time value, andfurther comprising computer implementable instructions which ifimplemented by the one or more processing units operatively enable thespecific apparatus to establish said plurality of code phase valuesbased, at least in part, on said plurality of encoded code phase values,said code phase origin reference value, and said reference time value.33. The article as recited in claim 31, wherein each of said pluralityof code phase values is established by subtracting said code phaseorigin reference value and a corresponding one of said plurality ofencoded code phase values from a reference time value.
 34. The articleas recited in claim 33, wherein said reference time value comprises alocal time value.
 35. The article as recited in claim 31, wherein saidspecific apparatus comprises a mobile station and said at least onemessage comprises acquisition assistance information signals sent by alocation server.
 36. The article as recited in claim 31, wherein saidspecific apparatus comprises a location server and said at least onemessage comprises pseudorange measurement information signals sent by amobile station.
 37. The article as recited in claim 31, wherein said atleast one message comprises at least one Position Determination DataMessage (PDDM).
 38. The article as recited in claim 31, wherein said atleast one SPS comprises at least one Global Navigation Satellite System(GNSS) and said at least one message comprises signals identifying saidat least one GNSS and at least one GNSS resource associated with atleast one of said plurality of encoded code phase values.
 39. Thearticle as recited in claim 38, wherein said GNSS resource comprises atleast one of a GPS resource, an SBAS resource, a QZSS resource, aGLONASS resource, a Galileo resource, and/or a Compass/BeiDou resource.40. The article as recited in claim 38, wherein said GNSS resource isassociated with at least one of a GNSS signal, a GNSS signal band,and/or a space vehicle (SV).